Maybe it's worth adding a section near ### List pseudotype about how the differences between Array and List are expressed throughout type signatures ([_] for List, Array _ for Array). I had to figure out the difference by reading the source. :)

Excellent suggestion, Aldwin! I will do so. :)

Please have another look at this pull request, @Avaq. :)

I see you switched to using regular brackets to remove ambiguity in nested type signatures. I'm curious about your reasoning. Other than that it looks good to me. :)

I see you switched to using regular brackets to remove ambiguity in nested type signatures. I'm curious about your reasoning.

I don't follow, I'm sorry.

I did, for example, change justs :: [Maybe a] -> [a] to justs :: Array (Maybe a) -> Array a. I did so because this function really does require an array of maybes. It would reject, for example, an arguments object of maybes.

Oh, whoops! I must have misread. It seems you were already using regular brackets before. I was talking about how I would write: Either[Error, Array String] where I think you would write Either Error (Array String). I somehow thought you changed between the two styles in this PR, but I was wrong.

I like to stay as true to the Haskell notation as possible, so I use Either a b rather than Either[a, b].

You're happy for this pull request to be merged otherwise?

I don't know where I got the square brackets from. I'll probably switch to using your haskellesk notation as well :). The changes look good to me by the way, feel free to merge.